Stop dumping every Dag to stdout when syncing FAB permissions - #70939
Merged
henry3260 merged 1 commit intoAug 3, 2026
Merged
Conversation
Left over from debugging; the sync_perm command already reports what it is doing, so this only adds one line of raw repr per Dag on top of it.
SameerMesiah97
approved these changes
Aug 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Left over from debugging; the sync_perm command already reports what it is doing, so this only adds one line of raw repr per Dag on top of it.
create_dag_specific_permissionsprinted every Dag's repr to stdout. It was addedin #53918, a refactor that had no reason to introduce output, and it is the only
bare
printin the FAB provider outsidecli_commands/— every other one carriesa human-readable message.
The
sync_permcommand already prints "Updating permission on all DAG views"before calling into this method, so the repr line is pure noise on top of it.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.